We have no control over the order in which scripts shut down

I think this should based on download_priority_group just like starting them on client, but reversed, eg. 9999 prio resource shutting down before 9998.

Nice! What code would u write in an onShutdown handler?

Nice! What code would u write in an onShutdown handler?

stopping resources in the right order to avoid problems with data saving. Read example from the link

Test if it working well in docker environment, i imagine you shutdown container and you want graceful save players, vehicles ect.

I'm telling you this because mta may not work well with docker and novadays most big servers are using it. Mta may not send proper signal to operating system what may lead to killing process before "onShutdown" end

You probably should do something like print("stopping"), then few queries like select sleep(1000) and print("stopped") to test if everything went all right

If somebody plans or runs an MTA server in Docker, they should use something like https://github.com/krallin/tini for launching the server executable for graceful and clean shutdowns.

Thanks, and please add it to wiki